PEPPOL Demystified: Complete Guide to the E-Invoicing Network (2025)

The Complete Guide to the World's Leading E-Invoicing Network

Updated: November 2025 | Reading Time: 30 minutes

Introduction: Why PEPPOL Matters

In an era where businesses exchange millions of electronic documents daily across borders, the need for a universal, secure, and interoperable network has never been greater. Enter PEPPOL—the Pan-European Public Procurement On-Line network that has evolved from a European initiative into the global standard for electronic document exchange.

With over 1.4 million registered participants from 98 countries and 6+ million documents exchanged monthly, PEPPOL has transformed how businesses and governments exchange invoices, purchase orders, and other procurement documents. Whether you're a finance professional preparing for Germany's 2025 e-invoicing mandate, an IT leader evaluating integration options, or a business owner seeking to streamline international transactions, understanding PEPPOL is essential.

This comprehensive guide demystifies PEPPOL: what it is (and what it's not), how the network architecture works, how to connect, and practical guidance for sending and receiving invoices through the network.

Chapter 1: What is PEPPOL?

Definition and Purpose

PEPPOL (now stylized as "Peppol") is a framework and network that enables the secure, standardized exchange of electronic business documents between organizations worldwide. It provides both the technical specifications for document formats and the network infrastructure for document delivery.

Think of PEPPOL like a global telecommunications network for business documents. Just as your mobile phone provider connects you to anyone else's phone regardless of their carrier, PEPPOL allows your business to exchange electronic invoices and other documents with any other PEPPOL participant—regardless of which service provider either party uses.

The Name Explained

Originally, "PEPPOL" stood for "Pan-European Public Procurement On-Line," reflecting its origins as an EU-funded project to simplify cross-border public procurement. In 2019, the acronym was retired in favor of the brand name "Peppol" to reflect its expanded scope beyond Europe and public procurement into global B2B commerce.

Key Components of PEPPOL

PEPPOL encompasses three interconnected elements:

The Network (eDelivery Network): The secure infrastructure connecting certified service providers (Access Points) worldwide, enabling document exchange between any participants.
The Standards (BIS Specifications): Business Interoperability Specifications defining the format and content of electronic documents, ensuring they can be processed automatically regardless of the sender's or receiver's systems.
The Governance (OpenPeppol): The non-profit association that develops specifications, certifies service providers, and maintains the network's integrity and security.

Chapter 2: What PEPPOL Is NOT

Understanding what PEPPOL isn't is just as important as understanding what it is. Here are the most common misconceptions:

PEPPOL Is NOT Software

PEPPOL is not an application you install on your computer. It's a set of standards and a network infrastructure. You interact with PEPPOL through software provided by certified service providers (Access Points) or through ERP/accounting systems that integrate with these providers.

PEPPOL Is NOT a Platform

Unlike centralized government e-invoicing platforms (such as Italy's SDI or Poland's KSeF), PEPPOL doesn't store or process your invoices centrally. It's a decentralized network where documents flow directly between Access Points without passing through a central government system.

PEPPOL Is NOT Limited to Invoices

While e-invoicing is the most common use case, PEPPOL supports a full range of procurement documents: purchase orders, order responses, catalogs, despatch advice, credit notes, and more. The network facilitates the entire procure-to-pay cycle.

PEPPOL Is NOT Only for Government Transactions

Despite its public procurement origins, PEPPOL is increasingly used for B2B transactions. In many countries, including Germany (from 2025), Belgium (from 2026), and Singapore, PEPPOL is becoming the standard for all business e-invoicing—not just government contracts.

PEPPOL Is NOT Automatic—Registration Is Required

Simply having a business doesn't mean you're on the PEPPOL network. Organizations must actively register through a certified Access Point provider and obtain a PEPPOL ID to send or receive documents.

Chapter 3: The History and Evolution of PEPPOL

Origins: A European Vision (2008-2012)

PEPPOL began in May 2008 as a Large Scale Pilot project funded by the European Commission under the Competitiveness and Innovation Programme. The EU invested over €15 million to solve a pressing problem: how could businesses from different countries, using different systems and standards, exchange procurement documents seamlessly?

A consortium of 11 European countries—Austria, Denmark, Finland, France, Germany, Greece, Italy, Norway, Portugal, Sweden, and the United Kingdom—collaborated to develop common technical standards for electronic procurement interoperability.

OpenPeppol Association (2012)

When the pilot project concluded in August 2012, the OpenPeppol Association was established in Belgium on September 1, 2012, as a non-profit organization to continue developing and maintaining the PEPPOL specifications. This transition from government project to independent association enabled PEPPOL to evolve beyond its original scope.

Global Expansion (2018-Present)

PEPPOL's transformation from a European initiative to a global standard accelerated in 2018 when Singapore became the first non-European Peppol Authority. Since then, adoption has spread to:

Asia-Pacific: Australia, New Zealand, Japan, Singapore, Malaysia
Europe: All EU member states plus Norway, Iceland, and the UK
Americas: Canada, USA (pilot), Mexico (pilot)
Middle East: UAE (implementing Peppol CTC model)

The PINT Era (2023)

In July 2023, OpenPeppol launched PINT (Peppol International Invoice Model), a breakthrough enabling countries with tax systems different from European VAT (such as GST in Australia and Singapore) to participate fully in the network. PINT and BIS 3.0 are expected to converge into BIS 4.0 in 2025-2026.

Chapter 4: How PEPPOL Works—The Network Architecture

The Four-Corner Model

PEPPOL operates on a "four-corner model"—an elegant architecture that enables any participant to exchange documents with any other participant through their respective service providers. The four corners are:

Corner 1 (C1) - The Sender: The business or organization sending the document (e.g., a supplier sending an invoice).
Corner 2 (C2) - Sender's Access Point: The certified service provider that connects the sender to the PEPPOL network. The Access Point validates the document, looks up the recipient's address, and transmits it.
Corner 3 (C3) - Receiver's Access Point: The certified service provider that connects the recipient to the PEPPOL network. This Access Point receives the document and delivers it to the recipient.
Corner 4 (C4) - The Receiver: The business or organization receiving the document (e.g., a buyer receiving an invoice).

The Document Exchange Process

Here's what happens when a supplier sends an invoice through PEPPOL:

Step 1: Document Creation The sender creates an invoice in their ERP or accounting system. The system (or Access Point) converts this to PEPPOL BIS format (structured XML).

Step 2: Recipient Lookup The sender's Access Point queries the PEPPOL directory using the recipient's PEPPOL ID to find:

Whether the recipient is registered on the network
Which Access Point serves the recipient
What document types the recipient can receive

Step 3: Validation The Access Point validates the document against PEPPOL BIS rules (format, required fields, business rules) before transmission.

Step 4: Secure Transmission Using the AS4 protocol with Transport Layer Security (TLS), the sender's Access Point transmits the document to the receiver's Access Point. Both parties authenticate using PKI certificates.

Step 5: Delivery The receiver's Access Point delivers the document to the recipient's system. The recipient receives a structured e-invoice that can be automatically imported into their accounting or ERP system.

Step 6: Confirmation The network provides delivery confirmation, and the recipient can optionally send an Invoice Response message back through the same process.

The Five-Corner Model (Peppol CTC)

As governments worldwide implement Continuous Transaction Controls (CTC) for real-time tax compliance, PEPPOL has evolved to include a five-corner model. This adds:

Corner 5 (C5) - Tax Authority: A government platform that receives tax-relevant data from invoices in real-time or near-real-time, enabling better VAT compliance and fraud prevention.

In the five-corner model:

Access Points at C2 and C3 may be required to obtain CTC certification
The sender's Access Point (C2) validates documents and reports to the tax authority (C5)
The receiver's Access Point (C3) also reports to C5
The exchange between C2 and C3 remains regulated by PEPPOL standards

Countries implementing or planning the five-corner model include Belgium, France, and the UAE.

Key Infrastructure Components

Service Metadata Locator (SML) The central directory operated by OpenPeppol that knows which Service Metadata Publisher (SMP) contains information about each participant. Think of it as a "phone book of phone books."

Service Metadata Publisher (SMP) A decentralized registry containing detailed information about participants: their PEPPOL ID, the document types they support, and their Access Point's technical address. Each Access Point typically operates its own SMP.

Access Points (AP) Certified service providers that connect organizations to the PEPPOL network. Access Points must:

Be members of OpenPeppol
Pass certification testing
Maintain ISO 27001 compliance (or equivalent)
Use OpenPeppol PKI certificates
Support the AS4 messaging protocol

Chapter 5: The PEPPOL ID—Your Digital Address

What Is a PEPPOL ID?

A PEPPOL ID (formally called a Peppol Participant Identifier) is your unique address on the PEPPOL network—similar to an email address or phone number. When someone wants to send you a document through PEPPOL, they use your PEPPOL ID to ensure it reaches the right destination.

PEPPOL ID Structure

A PEPPOL ID consists of two parts:

[Scheme Code]:[Identifier]

Scheme Code: A four-digit code indicating the type of business identifier being used. Different countries and identifier types have different scheme codes.

Identifier: Your actual business identification number (VAT number, company registration number, GLN, etc.).

Examples:

Country	Scheme Code	Example PEPPOL ID	Identifier Type
Germany	0204	0204:DE123456789	German VAT number
Austria	9915	9915:ATU12345678	Austrian VAT number
Netherlands	0106	0106:12345678	KvK number
Sweden	0007	0007:5567321707	Org. number
International	0088	0088:1234567891234	GLN (13 digits)

Common Identifier Types

Scheme	Code	Description	Use Case
GLN	0088	Global Location Number	International use, subsidiaries
DUNS	0060	Dun & Bradstreet number	Large enterprises
VAT	Various	National VAT numbers	Country-specific registration
LEI	0199	Legal Entity Identifier	Financial institutions

Multiple PEPPOL IDs

Organizations can have multiple PEPPOL IDs—for example:

Different IDs for different legal entities within a corporate group
Separate IDs for different departments or locations
Both a VAT-based ID and a GLN for different trading partners

Each legal entity must have its own unique PEPPOL ID; you cannot use one ID to cover multiple subsidiaries in different jurisdictions.

Chapter 6: How to Connect to PEPPOL

Option 1: Through an Access Point Provider (Recommended)

For most businesses, the simplest way to connect to PEPPOL is through a certified Access Point provider. This approach offers:

Advantages:

No technical infrastructure to maintain
Compliance handled by the provider
Format conversion and validation included
24/7 availability managed by experts
Often integrated with existing accounting/ERP systems

Steps to Connect:

Choose an Access Point Provider Select a certified Peppol Service Provider. Consider:
- Geographic coverage (especially for your trading partners' locations)
- Integration with your ERP/accounting system
- Document types supported
- Pricing model (per-document, subscription, or hybrid)
- Customer support quality
Register Your Organization Provide your business details:
- Company name and legal registration
- Business identification number (VAT, company number)
- Contact information
- Banking details (for invoice payments)
Obtain Your PEPPOL ID Your provider will assign a PEPPOL ID based on your business identifier and register it in their Service Metadata Publisher (SMP).
Configure Your Systems Connect your invoicing or ERP system to the provider's platform:
- API integration for automated exchange
- Web portal for manual invoice creation
- Email gateway for simpler use cases
Test and Go Live Exchange test documents with the provider to verify everything works, then begin production transactions.

Typical Timeline: Most businesses can be up and running within 1-5 business days.

Option 2: Become Your Own Access Point

Large enterprises or technology providers may choose to operate their own Access Point. This requires:

Requirements:

OpenPeppol membership (annual fee)
Signing the Transport Infrastructure Agreement (TIA)
Due diligence checks (company legitimacy, solvency, compliance)
Technical infrastructure meeting PEPPOL specifications
ISO 27001 certification or equivalent
AS4 messaging capability with 24/7 availability
PKI certificate from OpenPeppol
Passing interoperability and acceptance testing

Timeline: 3-6 months for full certification

When This Makes Sense:

You're a software vendor wanting to offer PEPPOL to customers
You process very high volumes (millions of documents annually)
You need complete control over the technical infrastructure
You want to resell PEPPOL services to other businesses

Option 3: Through ERP/Accounting Software

Many modern ERP and accounting systems include built-in PEPPOL connectivity:

Microsoft Dynamics 365: Native e-invoicing capabilities with PEPPOL support
SAP: Peppol integration through SAP Document Compliance
QuickBooks: Available through third-party connectors
Xero: PEPPOL integration in supported countries
Local solutions: Many regional accounting packages include PEPPOL

Check with your software vendor about native PEPPOL capabilities or recommended integration partners.

Chapter 7: PEPPOL Document Types

Core Billing Documents

Peppol BIS Billing 3.0 is the current standard for invoicing, supporting:

Document	Description	Use Case
Invoice	Standard commercial invoice	Requesting payment for goods/services
Credit Note	Invoice correction/cancellation	Correcting errors, processing returns
Invoice Response	Status feedback	Confirming receipt, approval, rejection

Procurement Documents

Document	Description	Use Case
Order	Purchase order	Requesting goods/services from supplier
Order Response	Order acknowledgment	Confirming order receipt and acceptance
Catalogue	Product/service catalog	Sharing pricing and product information
Catalogue Response	Catalog acknowledgment	Confirming catalog receipt
Despatch Advice	Shipping notification	Informing buyer of shipment details
Punch Out	Dynamic catalog	Real-time e-commerce integration
Order Agreement	Framework agreement	Documenting recurring arrangements

Document Validation

All PEPPOL documents undergo three levels of validation:

XML Schema Validation: Ensures the document structure conforms to UBL 2.1 specifications.
EN 16931 Validation: Verifies compliance with the European e-invoicing standard's business rules.
Peppol BIS Validation: Checks PEPPOL-specific rules using Schematron validation files.

Documents that fail validation are rejected before transmission, preventing errors from reaching recipients.

Chapter 8: Practical Examples—Sending and Receiving Invoices

Example 1: Sending an Invoice via PEPPOL

Scenario: A German supplier (Müller GmbH) needs to send an invoice to an Austrian buyer (Alpen AG).

Step-by-Step Process:

Create the Invoice Müller GmbH creates an invoice in their accounting system:
- Invoice number: INV-2025-0001
- Amount: €5,000.00 + €950.00 VAT
- Buyer reference: PO-2025-123
- Payment terms: Net 30 days
System Converts to PEPPOL Format The accounting system (or Access Point) converts the invoice to PEPPOL BIS Billing 3.0 format (UBL XML), including:
- Seller PEPPOL ID: 0204:DE123456789
- Buyer PEPPOL ID: 9915:ATU87654321
Validation The Access Point validates the invoice against PEPPOL rules before sending.
Recipient Lookup The Access Point queries the SML/SMP to find Alpen AG's Access Point and confirm they can receive invoices.
Transmission The invoice is securely transmitted to Alpen AG's Access Point using AS4 protocol.
Delivery Alpen AG receives the structured invoice directly into their ERP system—no manual data entry required.
Confirmation Alpen AG sends an Invoice Response (status: "Under Processing"), and later updates to "Approved."

Total Time: From send to receipt: typically under 10 minutes.

Example 2: Receiving Invoices via PEPPOL

Scenario: A Swiss company (Helvetia SA) wants to receive PEPPOL invoices from multiple suppliers.

Setup Process:

Register with an Access Point Helvetia SA signs up with a certified Peppol Access Point provider that serves Switzerland.
Obtain PEPPOL ID They receive their PEPPOL ID: 0106:CHE-123.456.789
Configure Document Types They register to receive:
- Invoices (PEPPOL BIS Billing 3.0)
- Credit Notes
- Invoice Responses (for sending status updates)
Integration Their ERP system is configured to:
- Pull incoming invoices from the Access Point via API
- Automatically match invoices to purchase orders
- Route to appropriate approvers
Communicate PEPPOL ID to Suppliers Helvetia SA informs suppliers of their PEPPOL ID and requests e-invoice delivery.

Daily Operations:

Invoices arrive in structured format throughout the day
ERP system automatically imports and validates
3-way matching (PO, receipt, invoice) happens automatically
Exceptions are flagged for human review
Approved invoices proceed to payment

What a PEPPOL Invoice Looks Like

Here's a simplified excerpt of a PEPPOL BIS 3.0 invoice structure (UBL XML):

<?xml version="1.0" encoding="UTF-8"?>
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">
  <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>
  <cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>
  <cbc:ID>INV-2025-0001</cbc:ID>
  <cbc:IssueDate>2025-11-15</cbc:IssueDate>
  <cbc:DueDate>2025-12-15</cbc:DueDate>
  <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
  <cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
  <cbc:BuyerReference>PO-2025-123</cbc:BuyerReference>
  
  <cac:AccountingSupplierParty>
    <cac:Party>
      <cbc:EndpointID schemeID="0204">DE123456789</cbc:EndpointID>
      <cac:PartyName>
        <cbc:Name>Müller GmbH</cbc:Name>
      </cac:PartyName>
      <!-- Additional supplier details -->
    </cac:Party>
  </cac:AccountingSupplierParty>
  
  <cac:AccountingCustomerParty>
    <cac:Party>
      <cbc:EndpointID schemeID="9915">ATU87654321</cbc:EndpointID>
      <cac:PartyName>
        <cbc:Name>Alpen AG</cbc:Name>
      </cac:PartyName>
      <!-- Additional buyer details -->
    </cac:Party>
  </cac:AccountingCustomerParty>
  
  <!-- Invoice lines, tax information, payment details -->
</Invoice>

Chapter 9: PEPPOL in the DACH Region

Germany: The B2B E-Invoicing Mandate

Germany has implemented the most comprehensive e-invoicing reform in the DACH region through the Wachstumschancengesetz (Growth Opportunities Act).

Timeline:

Date	Requirement
January 1, 2025	All businesses must be able to receive EN 16931-compliant e-invoices
January 1, 2027	Businesses with turnover >€800,000 must issue e-invoices for domestic B2B
January 1, 2028	All businesses must issue e-invoices for domestic B2B transactions

PEPPOL's Role in Germany:

Federal and national authorities must offer PEPPOL as a transmission option
KoSIT (Coordination Office for IT Standards) is the German Peppol Authority
XRechnung (German CIUS) is based on PEPPOL BIS standards
PEPPOL is recommended for secure, automated e-invoice exchange

Accepted Formats: XRechnung, ZUGFeRD 2.0.1+, Factur-X, PEPPOL BIS Billing 3.0

Austria: B2G Pioneer

Austria mandated B2G e-invoicing at the federal level since January 1, 2014—among the earliest in Europe.

Current Status:

B2G: Mandatory for federal government suppliers via e-Rechnung.gv.at or PEPPOL
B2B: Voluntary (no mandate, but PEPPOL widely used)
Formats: ebInterface 4.3/5/6, PEPPOL BIS Billing 3.0

Austria is monitoring the EU's ViDA directive for potential future B2B requirements.

Switzerland: QR-Bill Innovation

Although not an EU member, Switzerland aligns with European standards for government transactions.

Current Status:

B2G: Mandatory since January 1, 2016 for federal contracts ≥CHF 5,000
B2B: Entirely voluntary
Formats: swissDIGIN, ZUGFeRD/Factur-X, PEPPOL BIS
QR-Bill: Mandatory since October 2022 for payment slips (complements e-invoicing)

Swiss companies trading with EU partners should monitor the ViDA directive, which will require near-real-time e-reporting for cross-border B2B transactions by 2030.

Chapter 10: Benefits of PEPPOL

For Businesses

Cost Reduction

Processing costs drop from €10-30 per paper invoice to €1-3 per e-invoice
Eliminate postage, printing, and physical storage costs
Reduce labor costs through automation

Faster Processing

Invoice delivery in minutes instead of days
Automatic import eliminates data entry time
Accelerated approval workflows

Fewer Errors

Structured data eliminates manual entry errors
Validation catches problems before transmission
3-way matching becomes automated

Global Interoperability

"Connect once, connect to all"—one Access Point connection reaches all PEPPOL participants worldwide
No need for multiple point-to-point integrations
Standardized formats across borders

Enhanced Security

Authenticated senders and receivers via PKI certificates
Encrypted transmission protects sensitive data
Verified identities reduce invoice fraud risk

For Governments

Increased Tax Compliance

Real-time visibility into business transactions
Reduced VAT gap through better data
Automated cross-checking of reported transactions

Administrative Efficiency

Standardized processing across all suppliers
Reduced manual intervention in payment processing
Better spend analytics and procurement insights

Chapter 11: Common Mistakes and How to Avoid Them

Mistake 1: Assuming Directory Listing = Active Receiver

Just because an organization appears in the PEPPOL directory doesn't mean they're actively receiving documents. Always verify that recipients can receive your specific document type.

Mistake 2: Using PDF Invoices as Attachments

PEPPOL is designed for structured data exchange. Attaching PDF invoices defeats the purpose and may violate compliance requirements. The XML invoice data is the legally binding document.

Mistake 3: One PEPPOL ID for Multiple Legal Entities

Each legal entity needs its own PEPPOL ID. Using one identifier for multiple subsidiaries causes routing problems and compliance issues.

Mistake 4: Ignoring Validation Errors

PEPPOL validation exists for a reason. Don't try to bypass validation rules—fix the underlying data quality issues.

Mistake 5: Assuming All Access Points Are Equal

Access Points vary in geographic coverage, document type support, ERP integrations, and service quality. Choose a provider that matches your specific needs.

Conclusion: Getting Started with PEPPOL

PEPPOL has transformed from a European public procurement initiative into the global standard for electronic document exchange. With over 1.4 million participants worldwide, mandatory adoption in major markets like Germany, and continuous expansion into new regions, PEPPOL is no longer optional for businesses engaged in international trade.

Key Takeaways:

PEPPOL is a network, not software. Connect through certified Access Points or your ERP system.
The four-corner model enables universal connectivity. One connection reaches all participants worldwide.
Registration is required. Obtain your PEPPOL ID through an Access Point provider.
Multiple document types are supported. Beyond invoices—orders, catalogs, despatch advice, and more.
Compliance mandates are expanding. Germany 2025, Belgium 2026, France 2026—prepare now.

The transition to PEPPOL represents an opportunity to modernize your financial operations, reduce costs, accelerate cash flow, and prepare for the future of digital commerce. Whether you're facing an imminent compliance deadline or pursuing efficiency gains, the path forward is clear: connect to PEPPOL today.

Ready to Connect to PEPPOL?

TAPR AI offers comprehensive PEPPOL connectivity as part of our e-invoicing solution:

✅ Certified PEPPOL Access Point
✅ Full BIS 3.0 document support (invoices, credit notes, orders)
✅ AI-powered PDF conversion for vendors not yet PEPPOL-ready
✅ Vendor self-service portal for invoice creation
✅ Deep MS Dynamics 365 integration
✅ XML validation ensuring compliance

Last Updated: November 2025

Word Count: Approximately 4,500 words